- Created estate.property ORM model
- Added core property fields (name, description, postcode, prices, features)
- Defined garden orientation selection (North, South, East, West)
- Set required constraints on important fields (name, expected_price)
- Initialized estate_property database table via ORM

- Created ir.model.access.csv for estate.property model
- Added read, write, create and delete permissions
- Learned how Odoo security works using access rights
- Added security file in __manifest__.py
- Fixed access warning for estate.property model

- Added custom search view for estate properties
- Implemented search fields for property filtering
- Added predefined filters and group by functionality
- Practiced and understood search views, filters, domains, and group by concepts from Chapter 6 exercise

- Started Chapter 7 on relational fields
- Revised earlier Odoo tutorial chapters
- Reviewed models, views, ORM, and field concepts

- Fixed code formatting issues and removed unnecessary whitespace
- Cleaned up XML and Python structure for better readability
- Started learning relational fields (Many2one)
- Began exercises from the chapter on Many2one fields

- Studied Many2one field behavior and relationships
- Explored res.partner and res.users models
- Started implementing Many2one field exercises in estate module
- Improved understanding of relational fields in Odoo

- Learned Many2many stores recordsets (multiple linked records)
- Understood comodel_name defines target model relationship
- Learned optional relation table and column mapping behavior
- Understood ORM auto-generates relation table if not specified

- Added SQL constraints in estate models:
- property: expected_price > 0, selling_price >= 0
- offer: price > 0
- tag: UNIQUE(name)
- property type: UNIQUE(name

-Added model ordering for properties, offers, tags, and property types
-Added sequence field with manual ordering support for property types
-Configured property type field to disable create/edit from property form
-Added color field to tags and enabled color picker widget

- Added invisible rules for garden fields and offer buttons
- Restricted offer creation based on property state (readonly)
- Made list views editable for property, offer and tags
- Updated list view fields (optional date_availability, hidden by default)
- Added decorations for property and offer states
- Set default 'Available' filter and updated living area search domain

- Added stat button on estate.property.type to open estate.property.offer action using type='action'
- Displayed all related offers using offer_ids and offer_count in the view
- Implemented navigation from property type to offers list view via smart/stat button
- Added domain filter on estate.property.offer action to show only offers linked with active property type (property_type_id = active_id)

-Added business logic to CRUD methods
-Prevented deletion of properties unless state is 'New' or 'Cancelled'
-Updated property state to 'Offer Received' when creating offers
-Added validation to prevent lower offers than existing ones
-Added property_ids field to users with available properties domain

Created the Estate Account module to automatically generate invoices for sold
properties by integrating with the invoice functionality. When a property is
marked as sold, an invoice is created automatically, reducing manual effort and
streamlining the invoicing process for users and administrators.

Chapter 13: Interaction with Other Modules